-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support service entries in policy rules #1504
base: master
Are you sure you want to change the base?
Conversation
This follows API change on NSX that allows to specify explicit service entries on rule, as an alternative to service path. Signed-off-by: Anna Khmelnitsky <akhmelnitsky@vmware.com>
e2e16e3
to
3b2ed51
Compare
@annakhm, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
@annakhm, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
d4ecbe5
to
ac10ece
Compare
@annakhm, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
/test-all |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, let's rebase this and put order in the commit list to resolve the DCO complaint :)
This follows API change on NSX that allows to specify explicit service entries on rule, as an alternative to service path.